System and method for adjusting points assigned to a player in a player tracking system

ABSTRACT

A remote system and method for use with a gaming system for implementing a player tracking system for tracking points. The remote system includes a remote device and a remote network interface coupled to the remote device for exchanging data between a host computer and the remote device. The data includes adjustment information and information to adjust points associated with the player in the player tracking system.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional ApplicationSer. No.(not assigned), filed Sep. 11, 2003 (Attorney Docket No:60518,169) and is a continuation-in-part application of U.S. patentapplication Ser. No. 09/967,571, filed Sep. 28, 2001.

FIELD OF THE INVENTION

The present invention relates generally to gaming machines, and moreparticularly, to a system and method for remotely accessing the playertracking system.

BACKGROUND OF THE INVENTION

The growth and competition in the casino gaming market in recent yearsand the increasingly sophisticated and complex technology beingintegrated into the gaming environment, at the individual game, casinomanagement, and auditing levels, presents both challenges andopportunities to game manufacturers, gaming establishment operators, andregulatory agencies. The technological capabilities and requirements of,for example, advanced electronic games, multi-site gaming operations,detailed player tracking, wide area progressive jackpots, and variousalternatives to the use of currency and coins by players, all present apotentially huge pool of ever-changing data which can be of great valueto casino operators (from a management standpoint) and to regulatorsfrom an audit/compliance standpoint.

Players may also be given an incentive through a player tracking club.Usually, a player is identified during play by a player tracking ID cardand/or a player identification number (PIN). The player tracking systemtracks the player's play and awards player tracking points according toestablished criteria. The player tracking points may be redeemed forprizes, such as complimentary meals or merchandise.

Typically, the player tracking system is accessed at workstation orcomputers which are linked to a remote server. The computer applicationswhich are used to access the player tracking system for variousfunctions are stored on the workstation.

However, these types systems are inflexible and do not provide thecasino operator with the maximum benefit and advantages available fromthe information and systems now available.

The present invention is aimed at one or more of the problems as setforth above.

SUMMARY OF THE INVENTION

In one aspect of the present invention, a remote system for use with agaming system is provided. The gaming system implements a playertracking system for tracking points. The remote system includes a remotedevice and a remote network interface coupled to the remote device forexchanging data between a host computer and the remote device. The dataincludes adjustment information to adjust the points associated with aplayer in the player tracking system.

In another aspect of the present invention, a method for adjustingpoints associated with the player in a player tracking system isprovided. The method includes the steps of sending an adjustment form toa remote device and filling out the form with data by a user on theremote device for adjusting the points associated with the player in theplayer tracking system.

BRIEF DESCRIPTION OF THE DRAWINGS

Other advantages of the present invention will be readily appreciated asthe same becomes better understood by reference to the followingdetailed description when considered in connection with the accompanyingdrawings wherein:

FIG. 1 is a block diagram of a remote system for use with a gamingsystem, according to an embodiment of the present invention;

FIG. 2 is block diagram of an gaming machine and a remote device,according to an embodiment of the present invention;

FIG. 3 is a more detailed block diagram of the remote device of FIG. 2and a computer program application, according to an embodiment of thepresent invention;

FIG. 4 is a block diagram of a web client operating on the remote deviceof FIG. 2, according to an embodiment of the present invention;

FIG. 5A is a first flow diagram of a method for enrolling a player in aplayer tracking system, according to an embodiment of the presentinvention;

FIG. 5B is a second flow diagram of a method for enrolling a player in aplayer tracking system, according to a second embodiment of the presentinvention;

FIG. 6 is a diagrammatic illustration of a remote player signup formaccording to an embodiment of the present invention;

FIG. 7A is a first flow diagram of a method for remotely accessingplayer information, according to an embodiment of the present invention;

FIG. 7B is a second flow diagram of a method for remotely accessingplayer information, according to a second embodiment of the presentinvention;

FIG. 8 is a diagrammatic illustration of a remote player informationscreen, according to an embodiment of the present invention;

FIG. 9A is a first flow diagram of a method for remotely accessinginformation related to a device, according to an embodiment of thepresent invention;

FIG. 9B is a second flow diagram of a method for remotely accessinginformation related to a device, according to a second embodiment of thepresent invention;

FIG. 10 is a diagrammatic illustration of a remote asset informationscreen, according to an embodiment of the present invention;

FIG. 11A is a first flow diagram of a method for remotely processingjackpot tickets, according to an embodiment of the present invention;

FIG. 11B is a second flow diagram of a method for remotely processingjackpot tickets, according to a second embodiment of the presentinvention;

FIG. 12 is a diagrammatic illustration of a cash ticket informationscreen, according to an embodiment of the present invention;

FIG. 13A is a first flow diagram of a method for remotely processingjackpot tickets, according to an embodiment of the present invention;

FIG. 13B is a second flow diagram of a method for remotely processingjackpot tickets, according to a second embodiment of the presentinvention;

FIG. 14A is a diagrammatic illustration of a jackpot information screen,according to an embodiment of the present invention;

FIG. 14B is a diagrammatic illustration of a fill information screen,according to an embodiment of the present invention;

FIG. 15A is a first flow diagram of a method for remotely processinghopper fills, according to an embodiment of the present invention;

FIG. 15B is a second flow diagram of a method for remotely processinghopper fills, according to a second embodiment of the present invention;

FIG. 16A is a diagrammatic illustration of a hopper fill informationscreen, according to an embodiment of the present invention;

FIG. 16B is a diagrammatic illustration of a fill information screenaccording to an embodiment of the present invention;

FIG. 17A is a first flow diagram of a method for remotely providing atable rating interface, according to an embodiment of the presentinvention;

FIG. 17B is a second flow diagram of a method for remotely providing atable rating interface, according to a second embodiment of the presentinvention;

FIG. 18A is a diagrammatic illustration of an open table rating screen,according to an embodiment of the present invention;

FIG. 19A is a first flow diagram of a method for remotely providing anattendance interface, according to an embodiment of the presentinvention;

FIG. 19B is a second flow diagram of a method for remotely providing anattendance interface, according to a second embodiment of the presentinvention;

FIG. 20 is a diagrammatic illustration of a player attendanceinformation screen, according to an embodiment of the present invention;

FIG. 21A is a first flow diagram of a method for remotely providing asurveillance interface, according to an embodiment of the presentinvention;

FIG. 21B is a second flow diagram of a method for remotely providing asurveillance interface, according to a second embodiment of the presentinvention;

FIG. 22 is a diagrammatic illustration of an alert information screen,according to an embodiment of the present invention;

FIG. 23A is a flow diagram of a first method for adjusting pointsassigned to a player in a player tracking system, according to anembodiment of the present invention;

FIG. 23B is flow diagram of a second method for adjusting pointsassigned to a player in a player tracking system, according to anotherembodiment of the present invention;

FIG. 24 is a diagrammatical illustration of a point adjustment requestform, according to an embodiment of the present invention;

FIG. 25A is a flow diagram of a method for issuing vouchers to a player,according to an embodiment of the present invention;

FIG. 25B is a flow diagram of a second method for issuing vouchers to aplayer, according to another embodiment of the present invention;

FIG. 26 is a diagrammatic illustration of a voucher information screen,according to an embodiment of the present invention;

FIG. 27A is a flow diagram of a method for redeeming printed vouchersusing a remote device, according to an embodiment of the presentinvention;

FIG. 27B is a flow diagram of a second method for redeeming printedvouchers using a remote device, according to an embodiment of thepresent invention;

FIG. 28 is a diagrammatic illustration of a voucher information form,according to an embodiment of the present invention;

FIG. 29A is a first flow diagram of a method for displaying a list ofoutstanding vouchers for a selected player, according to a firstembodiment of the present invention;

FIG. 29B is a second flow diagram of a method for displaying a list ofoutstanding vouchers for a selected patron, according to a secondembodiment of the present invention; and

FIG. 30 is a diagrammatic illustration of a voucher informationdialogue, according to an embodiment of the present invention.

DETAILED DESCRIPTION OF INVENTION

I. Overview

With reference to the drawings and in operation, the present inventionprovides a system 10 and methods related to a player tracking method orto one or more gaming devices 12.

The gaming devices 12 may be electronic or electric gaming machines 13,such as slot or video slot machines, poker or video poker machines,arcade or video arcade games, and the like, but may also include othertypes of devices 12A connected to the system 10, such as virtual gamingmachines (for online gaming), electronic interfaces for use with tablegames, vending machines, token or credit dispensing machines, ticketredemption machines, or any other electric or electronic deviceconnected to the network.

II. The Gaming System

In one embodiment, the system 10 and methods may be embodied orimplemented via an entertaining management and monitoring system orgaming system 14 which is shown in block diagram form in FIG. 1. Theentertainment and monitoring system 14 may include may additionalfunctions such as, real-time multi-site, slot accounting, playertracking, cage credit and vault, sports book data collection, Point ofSale (POS) accounting, keno accounting, bingo accounting, and table gameaccounting, a wide area progressive jackpot, and electronic fundstransfer (EFT). Two exemplary systems are disclosed in U.S. patentapplication Ser. No. 09/967,571. filed Sep. 28, 2001, and U.S.Provisional Patent Application Ser. (Not Assigned), filed Sep. 11, 2003(Attorney Docket No. 60,518-169), both of which are hereby incorporatedby reference.

In the illustrated embodiment, the system 10 includes eight electronicgaming machines 13A-13H. However, it should be noted that the presentinvention is not limited to any number of devices 12 or machines 13. Inone embodiment, the machines 13 are organized into banks (not shown),each bank containing a plurality of machines 13.

The gaming devices 12 are connected via a network 16 to one or more hostcomputers 18, which are generally located at a remote or centrallocation. The computer 18 includes a computer program application 20which maintains one or more databases 22. In one embodiment, thedatabase(s) are Oracle database(s).

The computer program application 20 and databases 22 may be used torecord, track, and report accounting information regarding the gamingdevices 12 and/or users of the gaming devices 12 or players of theelectronic gaming machines 13. Additionally, the computer programapplication 20 and databases 22 may be used to maintain informationrelated to player tracking accounts (see below).

In general, the electronic gaming machines 13 are playable by a player24. The player 24 may select one of the electronic gaming machines 13Cto play and insert a coin, credit, coupon, and/or player tracking card(not shown) into the chosen gaming machine 13C. Generally, theelectronic gaming machines 13C have an associated number of credits orcoins required in order to play. In the case of video slot or pokergames, the game is played and an award in the form of credits may beawarded based on a pay table of the gaming machine 13.

With reference to FIG. 2, a block diagram of a suitable electronicgaming machine 13C is shown.

The machine 13C comprises a game controller 26, or central processingunit (CPU), a coin-bill management device 28, a display processor 30, aRAM 32 as a memory device and a ROM 34 (generally provided as an EPROM).The CPU 26 is mainly composed of a microprocessor unit and performsvarious calculations and motion control necessary for the progress ofthe game. The coin-bill management device 28 detects the insertion of acoin or a bill and performs a necessary process for managing the coinand the bill. The display processor 30 interprets commands issued fromthe CPU 26 and displays desirable images on a display 36. The RAM 32temporarily stores programs and data necessary for the progress of thegame, and the ROM 34 stores, in advance, programs and data forcontrolling basic operation of the machine 12C, such as the bootingoperation thereof, game code and graphics.

Input to the gaming device 12C may be accomplished via mechanicalswitches or buttons or via a touchscreen interface (not shown). Suchgaming machines 12 are well known in the art and are therefore notfurther discussed.

The player 24 is identified via the player tracking card and/or a playeridentification number entered into player tracking device 38 at eachgaming machine 12 (see below). Player tracking accounts may be used,generally, to provide bonuses to a player, in addition to the awarddesignated by, in the case of a video slot or poker machine, the gamingmachine's 12 paytable. These bonuses may be awarded to the player 24based a set of criteria, including, but not limited to, a) the player'splay on the machine 12C, b) the player's overall play, c) play during apredetermined period of time, and d) the player's birthday oranniversary, or e) any other definable criteria. Additionally, bonusesmay be awarded on a random basis, i.e., to a randomly chosen player orrandomly chosen game 12. Bonuses may also be awarded in a discretionarymanner or based on other criteria, such as, purchases made at a giftshop or other affiliated location.

In one embodiment, the player tracking device 38 includes a processor40, a player identification card reader 42 and/or a numeric keypad 44,and a display 46. In one embodiment, the display 46 is a touchscreenpanel and the numeric keypad 44 is implemented thereon.

The player 24 may be identified by entry of a player tracking card intothe player identification card reader 42 and/or entry of a playeridentification number (PIN) on the numeric key pad 46. The play trackingdevice 38 may also be used to communicate information between thecomputer 18 and the corresponding gaming machine 12C. The playertracking device 40 may also be used to track bonus points, i.e.,incentive points or credits, downloaded from the computer 18.

In one aspect of the present invention, the bonuses are awarded as bonuspoints. In one embodiment, the bonus points are incentive points. Inanother embodiment, the bonus points are credits.

The incentive points may converted to credits using a predeterminedratio. The predetermined ratio may be 1 or any other desired ratio. Thepredetermined ratio may also be varied based on determined criteria,e.g., the gaming machine 12 being played, the player, or the time ofday. Incentive points may be designated as cashable or non-cashable. Theincentive points in a player account may be downloaded to one of thegaming machines 12 for play.

III. Remote System

Returning to FIG. 1, the present invention provides a remote system 48for use with the gaming system 14. The remote system 48 provides accessto various features or functions of the gaming system 14 by one or moreremote devices 50.

In the illustrated embodiment, there are four remote devices 50A, 50B,50C, 50D, however, this is for discussion purposes only. Any number ofremotes devices 50 may be included.

The remote devices 50 are connected to the network 16 through a networklink 52. In one aspect of the present invention, the network link 52 isa wireless connection. In one embodiment, the wireless connection usesthe IEEE 802.11 standard, e.g., 802.11b or 802.11g. However, it shouldbe noted that wireless links using other standards may also be usedwhere appropriate, such as a short range radio link (e.g., a link usingthe technology known as “Blue Tooth”). In another aspect of the presentinvention, the network link 52 may be a wire link.

The remote devices 50 are generally used by a user 54 and provides, asdiscussed below, access to various data and/or functions of the gamingsystem 14.

In one aspect, the user 54 is an employee of the gaming establishedwhere the gaming system 14 is operating. Typically, the user 54 has anassigned role (or type) based on their job description. Typical rolesmay include, but are not limited to, system administrator, supervisor,pit, pit manager, slot floor employee, patron host, player's club,security, security supervisor, slot attendant, slot director, slot shiftsupervisor, slot technician, sports and racebook, surveillance, andtable supervisor.

In one embodiment of the present invention, the remote devices 50provides access to one or more types of data and/or one or morefunctions based on the assigned role of the user 54. In one embodiment,a remote device 50 may provide access to one or more of the followingfunctions: remote patron signup, remote patron information, remotedevice information, remote cash ticket processing, remote jackpot ticketprocessing, remote hopper fill ticket processing, remote table ratinginterface, remote attendance, remote surveillance, adjusting a player'sbonus or comp points, issuing comp vouchers to a player, redeemingprinted vouchers, listing and redeeming outstanding vouchers assigned toa player, and retrieving and displaying information related to aspecific remote device 50. Each of these functions is described morefully below.

In one embodiment of the present invention, the remote device 50A may bea mobile computer based on the PALM operating system or MicrosoftWindows operating system. With specific reference to FIG. 3 in oneembodiment of the present invention, the remote device 50A includes aprocessor 58, a memory 60 for storing applications and data, and adisplay 64. The display 64 may be a touchscreen display. The remotedevice 50A may also include a bar code reader 66. The bar code reader 66may be used to read a player ID card number from the ID card or to reada device ID number from a device 12 (see below). One such mobilecomputer is available from Symbol Technologies, Inc. of Holtsville, N.Y.as model number SPT 1800.

Additionally or alternatively, the remote device 50A may include an IDcard reader 62 capable of reading magnetic stripe ID cards.

In another embodiment, the remote devices 50 are desktop, laptop,notebook, and/or sub-notebook computers.

Returning to FIG. 3, in one embodiment of the present invention, theremote device 50A includes a web client 56 which is stored in the memory60 and run on the processor 58. The web client 56 is connected to thecomputer program application 20 running on the host computer 18 throughthe network link 52.

In one aspect of the present invention, all interaction with the user,including the display of data and queries and the input of data, ishandled by the web client 56. The web client 56 is responsible foracquiring user input, e.g., through forms, and formatting and presentinginformation to the user 54. The web client 56 is a computer applicationwhich is accessed via a web browser, such as Microsoft InternetExplorer, available from Microsoft Corp., of Redmond Calif. The webclient 56 may be written in Hypertext Mark-Up Language (HTML) andinclude one or more servlets (see below) which may be written in acomputer programming language, such as Java.

As shown in FIG. 3, the computer program application 20 implements aremote network interface 66. The remote network interface 68 couples theweb client 56 with the database 22. In one embodiment, the remotenetwork interface 68 obtains data from the database 22, formats thedata, e.g., into an HTML response, and returns the formatted data to theweb client 56.

In one aspect of the present invention, the remote network interface 68is coupled to the database 22 by one or more data objects 70. In oneembodiment, data is stored in the database 22 in data tables. The dataobjects 70 handle requests from the remote network interface 68,abstracts the required data from the database tables and/or sets datainto the database tables.

As shown, in FIG. 3, the data objects 70 include a plurality of firstdata object (DBOBJECTS) 76, at least one second data object (VDBOBJECTS)74, and a third data object (BUSINESS OBJECT) 72.

The first data objects 76 are coupled to the database tables andabstract specific database tables for the at least one second dataobject 74. The first data objects 76 handle retrieving and setting datainto specific database tables.

The at least one second data object 74 is coupled to the first dataobjects 76 assemble multiple first data objects 76 into a single thirddata object 72. The at least one second data object 74 abstract thethird data object 72 from the database tables.

The third data object 72 is coupled to the at least one second dataobject 74. The third data object receives queries from the remotenetwork interface, retrieves responsive data from the database (throughthe first and second data objects 74,76), formats the responsive dataand returns the responsive data to the remote network interface.

With reference to FIG. 4 in one embodiment, the web client 56 is writtenin HTML. In the illustrated embodiment, the web client 56 includes aform layer 78, a menu layer 80, a login layer 82, and a servlet layer84.

The login layer 82 provides security. It allows the user 54 to logon tothe remote system 48. In one embodiment, the user 54 enters a name andpassword to logon. The user 54 may also be required to enter or selectthe site at which the user 54 is located.

The menu layer 90 allows the user 54, once logged on, to navigate to andbetween servlets. The servlets are downloaded to the remote device 50from the hose computer 18 as needed. The menu layer 90 also handlesproviding access to those servlets to which the user 54 has access,typically based on an assigned role (see above).

The form and servlet layers 78, 84 provides common functionality for theservlets.

A. Remote Player or Patron Signup

With reference to FIGS. 5A, 5B, and 6, the remote system 48 allows theuser 54, such as a slot floor employee or patron host to quickly andremotely enroll a player or patron in the player tracking system. Theuser 54 will generally have a number of unassigned player ID cards (notshown). The user 54 may be approached by a player 24 who requests toenroll or may approach the player 24 and ask if they would want toenroll.

If the player 24 wants to enroll, the user 54 enters sign-up informationor data onto the remote device 50A and gives the player 24 a player IDcard. The sign-up information is sent by the remote device 50A to thehost computer 18 and stored in the database 22 along with the ID cardnumber of the assigned player ID card.

In one embodiment, the user 54 navigates to a servlet for enrolling theplayer 24 using the menu layer 80. The menu layer 80 requests theservlet from the host computer 18 from which it is then downloaded tothe remote device 50A.

In one embodiment, only the player's name and a player identificationnumber (PIN) is required. The player identification number may beselected by the player 24 or be a temporary default PIN assigned to theplayer ID card. The player ID card number to be assigned to the player24 may be read by the ID card reader 62 or the barcode reader 66, asappropriate.

When the user 54 selected enrollment from the menu layer, the web client56 relays the request to the remote network interface 68. The remotenetwork interface 68 retrieves a signup form and sends the signup formto the remote device 50A for display and interaction with the user 54via the web client 56.

With specific reference to FIG. 5A, a first method 88 for enrolling theplayer 24 in the player tracking system using the remote device 50A,according to a first embodiment of the present invention is shown. In afirst step 90, a fillable signup form is sent to the remote device 50A.In a second step 92, the player information (or enrollment data) isentered on the signup form via the remote device 50A.

With specific reference to FIG. 5B, a second method 94 for enrolling theplayer 24 in the player tracking system using the remote device 50A,according to a second embodiment of the present invention is shown.

In a first step 96, the signup form is displayed on the remote device50A. In a step 98, if all required information, e.g., a zip code, wasentered then the method 94 proceeds to a third step 100. If all requiredinformation was not entered, then an error message is displayed in afourth step 102 and the process returns to the first step 96.

In the third step 100, the zip code is processed, i.e., thecorresponding city and state are determined. In a fifth step 104, if thezip code is not valid, then the method 94 displays an error message(fourth step 102). If the zip code is valid, then the method 94 proceedsto a sixth step 106.

In the sixth step 106, the enrollment data is stored are stored asrecords in the database 22 and control proceeds to a seventh step 108.In the seventh step 108, if a room number, i.e., the hotel room hotel inwhich the player 24 is residing was entered, then the process proceedsto an eighth step 110. Otherwise, the method 96 returns to the firststep 96.

In the eighth step 110, an external system (not shown), may be notifiedfor the creation of room lock keys. One such system In one embodiment asdiscussed below, the room lock keys may be used for the player trackingsystem and/or room locks.

An exemplary signup form 110, displayed on the remote device 50A by theweb client 56 is shown in FIG. 6. As discussed above, in one embodimentthe only information required is the player's name and a PIN number. Theexemplary signup form 110 includes an entry box for the player's first,middle, and last names 112, 114, 116 and a PIN entry box 118. After therequired information has been entered, the user 54 selects a save playerbutton 120 to send the data to the host computer 18.

In another embodiment, the signup form 110 requires additionalinformation. The additional information may include, but is not limitedto the following: player ID card number (from pre-printed card or leftblank for system generated card), address, zip code, country, telephonenumber(s), room number, number of adult cards, number of child cards,signup date, and one or more notes. Child cards operate only the lock ofa hotel room. Adult cards work in the player tracking system and operatethe room lock.

Additionally as discussed above, the display 46 is a touchscreendisplay. In one embodiment, the display may capture a signature of theplayer 24. The player's signature may be also be sent to the hostcomputer 18 with the enrollment data and stored in the database 22.

B. Remote Patron Information

With reference to FIGS. 7A, 7B, and 8, the remote system 48 allows theuser 54, such as a slot floor employee or patron host to quickly andremotely request and receive player information related to a specificplayer 24. This may be done prior to approaching the player 24 who isusing a specification gaming machine 13 or after the user 54 has beenapproached by the player 24.

In the illustrated embodiment, interaction with the user 54, includingreceiving input and displaying the player information, is accomplishedusing the web client 56.

In one aspect of the present invention, the user 54 may identify theplayer 24 through entry of the player's ID card number into the remotedevice 50A. In one embodiment, the ID card number may be enteredmanually. In another embodiment, the ID card number may be read from theplayer's ID card using the card reader 62 or the barcode reader 66 asappropriate.

In another aspect of the present invention, if the player 24 isutilizing one of the devices 12 and has identified themselves to theplayer tracking system by entry of the ID card into the device 12 and/orentered in their PIN number, the user 54 may identify the player 24 byentered a device ID number associated with the respective device 12. Asdiscussed below, the player tracking system has associated the ID numberof the device 12 with the player 24 while the player 24 is using thedevice 12. Thus, using the device ID number, the host computer 18 maydetermine the ID number of the player 24.

In one embodiment, the user 54 navigates to a servlet for requestingplayer information using the menu layer 80. The menu layer 80 requeststhe servlet from the host computer 18 from which it is then downloadedto the remote device 50A.

The servlet displays a request form which is displayed to the user 54.As discussed above, the user 54 may either enter the player I) cardnumber of the player 24 (manually or reading it from the ID card) or adevice ID number associated with a device 12 being used by the player24. The user 54 enters identification information (in the form of theplayer ID card number or the device ID number) which is returned to thehost computer 18 by the web client 56. The remote network interface 68receives the identification information, retrieves the playerinformation and returns the player information to the remote device 50Awhere it is displayed.

With specific reference to FIG. 7A, a first method 124 for remotelyrequesting information relating to a player 24 is provided. In a firststep 126, identification information is received at the remote device.In a second step 128, the identification information is received at thehost computer. In a third step 130, the player information is retrievedfrom the database 22 as a function of the identification information.

With specific reference to FIG. 7B, a second method 132 for remotelyrequesting player information using the remote device 50A is shown,according to a second embodiment of the present invention.

In a first step 134, the request form is displayed on the remote device50A. In a second step 136, if a player ID card number has been entered,then the method 132 proceeds to a third step 138. In the third step 138,the ID card number is validated. In a fourth step 140, if the ID cardnumber is not valid, an error message is displayed in a fifth step 142.If the ID card number is valid, then the message proceeds to a sixthstep 144.

In the sixth step 144, the query (request for player information) isprocessed by the host computer 18. The player (or patron) information isthen returned to the remote device 50A to be displayed in an seventhstep 146.

In the second step 136, if an ID card number has not been entered, thenthe method 132 proceeds to an eighth step 148. In the eighth step 148,if a device (or asset) number has been entered, then the method 132proceeds to a ninth step 150. If a device number has not been entered,then the method 132 proceeds to the fifth step 142 and an error messageis displayed.

In the ninth step 150, the device number is validated. In a tenth step152, if the device number is valid, then control proceeds to the fifthstep 144. Otherwise, the method 132, proceeds to the fifth step 142.

With specific reference to FIG. 8, in one embodiment the returned playerinformation is displayed on the remote device 50A in a playerinformation screen 152. In the illustrated embodiment, the playerinformation may include, but is not limited to, a player name, a playeraddress, a patron host name, at least one anniversary date, e.g.,birthday, wedding anniversary, sign-up date, any meters tracked by theplayer tracking system, such as bonus points (incentive points orcredits), jackpots, coin-out, coin-in, and win/(loss).

C. Remote Device Information

With reference to FIGS. 9A, 9B and 10, the remote system 48 allows theuser 54, such as a slot floor employee or a slot technician, to quicklyremotely request and receive asset or device information related to angaming device 12.

In the illustrated embodiment, interaction with the user 54, includingreceiving input and displaying the asset information is accomplishedusing the web client 56.

In one aspect of the present invention, the user 54 may identify thegaming device 12, such as an electronic gaming machine 13 by enteringidentification information. In one embodiment, the identificationinformation is an asset or device ID number. The ID number may bemanually entered by the user 54. In another embodiment, the user 54 mayuse the barcode reader 66 to read a barcode, located on the gamingdevice 12, containing the device ID number.

In one embodiment, the user navigates to a servlet for requested deviceinformation using the menu layer 80. The menu layer 80 requests theservlet from the host computer 18 from which it is then downloaded tothe remote device 50A.

The servlet displays a request form (not shown) which is displayed tothe user 54. After the asset or device ID number entered, the ID numberis sent to the remote network interface 68, which process the query, andreturns the requested device information to the remote device 50A whereit is displayed.

With specific reference to FIG. 9A, a first method 154 for remotelyrequesting information related to a specific gaming device 12 isprovided. In a first step 156, identification information is received atthe remote device 50A. In a second step 158, the identificationinformation is received at the host computer 18. In a third step 160,the device information is retrieved from the database 22 as a functionof the identification information.

With specification reference to FIG. 9B, a second method 162 is forremotely requesting device information using the remote device 50A isshown, according to an embodiment of the present invention.

In a first step 164, the request form is displayed on the remote device50A. In a second step 166, if an asset number has been entered then themethod 162 proceeds to a third step 170. Otherwise, an error message isdisplayed in a fourth step 168.

In the third step 170, the asset number is validated. In a fifth step172, if the asset number is valid then the method 162 proceeds to asixth step 174. In the sixth step 174, the query (request for assetinformation) is processed by the host computer 18. The device or assetinformation is returned to the remote device 50A to be displayed in aseventh step 176.

With specific reference to FIG. 10, in one embodiment the returned assetinformation is displayed on the remote device 50A in a remote assetinformation screen 178. In the illustrated embodiment, the assetinformation may include, but is not limited to, an asset number, adevice number, a denomination (the base denomination the deviceaccepts), a manufacturer, a model, a master prom identifier, a game promidentifier, an online MAC address, an online TCP/IP address, a date onfloor, and any or all available system meters, such as, coin in, coinout, games player, and jackpots.

D. Remote Cash Ticket Processing

In one embodiment, a gaming system includes a gaming machine that mayissue a cash ticket. The cash ticket is issued when a player elects toquit playing a particular gaming machine after accumulating a number ofcredits. The number of credits is generally the sum of an originalnumber of credits, any downloaded credits, any inserted credits, and anywinnings (or losses).

With reference to FIGS. 11A, 11B and 12, the remote system 48 allows theuser 54, such as a slot floor employee or patron host to quickly andremotely process a cash ticket issued by a particular gaming machine 13.The cash ticket issued by the gaming machine 13 includes cash ticketinformation such as a cash ticket id and a value printed on the cashticket. The user 54 may be approached by a player 24 who requests tocash out a cash ticket and receive the value of the cash ticket.

If the player 24 wants to cash out, the user 54, via the remote device50A, requests a cash ticket form. The remote network interface 68 sendsthe cash ticket form to the remote device 50A.

When the user 54 selects the cash ticket form from the menu layer 80,the web client 56 relays the request to the remote network interface 68.The remote network interface 68 retrieves the cash ticket form and sendsthe cash ticket form to the remote device 50A for display andinteraction with the user 54 via the web client 56.

The cash ticket form may include a cash ticket button for selecting bythe user 54 to communicate each step of the cash ticket processing thathas occurred. For example, the cash ticket button is a request buttonthat the user 54 selects when the user 54 is approached by the player24. The cash ticket button may be an acknowledge button selected by theuser 54 after validating the cash ticket and prior to processing thecash ticket. The cash ticket button may also be a process buttonselected by the user 54 after confirming that the cash ticket may bepaid. The cash ticket button may also be a paid button to confirm thatthe user 54 has paid to the player 24 the value of the cash ticket. Eachtime the cash ticket button is selected by the user 54, the remotedevice 50A sends a notification of the event and the remote networkinterface 68 stores the notification in the host computer 18 which thenupdates the data in the database 23 relating to the status of the cashticket processing.

The cash ticket form may also include a field wherein the user 54 entersthe cash ticket id such as a number. The user 54 enters cash ticketinformation or data onto the remote device 50A to verify that the cashticket is valid and has not been previously processed. If the cashticket id is invalid or the cash ticket has already been processed, anerror message is displayed at the remote device 50A. The cash ticketinformation is sent by the remote device 50A to the host computer 18where cash ticket information is retrieved and sent back to the remotedevice 50A. In one embodiment, the cash ticket id is entered manually,then the user 54 selects a cash ticket entry button to send the cashticket form to the host computer 18. In another embodiment, the cashticket id is encoded in a barcode printed on the cash ticket. The barcode is read by the bar code reader and sent to the host computer 18.

In one embodiment, the user 54 navigates to a servlet 24 using the menulayer 80 for inputting and retrieving cash ticket information. The menulayer 80 requests the servlet from the host computer 18 from which it isthen downloaded to the remote device 50A.

After the validity of cash ticket is confirmed, the cash ticketinformation is retrieved from the database 22 by the remote networkinterface 68 and displayed to the user 54 at the remote device 50A. Withspecific reference to FIG. 12, in one embodiment the returned cashticket information is displayed on the remote device 50A in a cashticket information screen 196.

The cash ticket information includes ticket details 168, such as agaming machine identifier. The gaming machine identifier includes agaming machine id and a gaming machine location to identify the gamingmachine issuing the cash ticket. The ticket details 168 further includea date identifier for identifying the issue date of the cash ticket, ashift identifier for identifying the work shift during which the cashticket was issued, and a value identifier for identifying the value ofthe cash ticket, thereby allowing the user 54 to confirm the valueprinted on the cash ticket and the value stored in the host computer 18.

With specific reference to FIG. 11A, a first method 170 for processing acash ticket using the remote device 50A, according to a first embodimentof the present invention is shown. In a first step 172, a fillable cashticket form is sent to the remote device 50A. In a second step 174, thecash ticket information is entered on the cash ticket form via theremote device 50A.

With specific reference to FIG. 11B, a second method 176 for processingthe cash ticket using the remote device 50A, according to a secondembodiment of the present invention is shown.

In a first step 178, the cash ticket form is displayed on the remotedevice 50A. In a second step 180 a cash ticket id is entered. In a thirdstep 182, the cash ticked id is verified. If the cash ticket id isinvalid, then the method 176 proceeds to a fourth step 184. If the cashticket id corresponds to a valid unprocessed cash ticket, then themethod 178 proceeds to a fifth step 186. In the fourth step 184, anerror message is displayed and the method 176 returns to the first step178.

In the fifth step 186, the ticket details are retrieved from thedatabase 22 and control proceeds to a seventh step 188. In the seventhstep 188, the ticket details are processed and display at the remotedevice 50A. The user 54 may then pay the player. As discussed above, theuser may be required to acknowledge through the selection of the cashticket button at each step. Once the user has acknowledged that theplayer has been paid, , the remote display displays a cash ticket paidmessage in an eighth step 190.

E. Remote Jackpot Ticket Processing

In one embodiment, a gaming system includes a gaming machine that mayissue a jackpot ticket. In one embodiment, a jackpot ticket is issued bythe gaming machine when a play of the game results in a win having anassociated number of credits over a predetermined number of credits.Such a jackpot causes the gaming machine 12 to lock up, issue an alertand prevents the player from playing.

In another embodiment, the gaming machine 12 does not issue jackpotticket. However, the user 54 may be required to go to the gaming machine12 to process the jackpot

With reference to FIGS. 13A, 13B and 14A, the remote system 48 allowsthe user 54, such as a slot floor employee, to quickly and remotelyprocess a jackpot issued by a particular gaming machine 13. The jackpotissued by the gaming machine 13 has associated jackpot information suchas a jackpot id and a value of the jackpot.

In one embodiment, the jackpot is dispensed by the gaming machine 13,while jackpots above the threshold require interaction with an employee,i.e., the user 54. Additionally, the jackpot may be required to be paidby a cashier. If a jackpot ticket has been issued, the user 54 may beapproached by a player 24 who requests to collect the value of thejackpot. Alternatively, the user 54 may have to travel to the gamingmachine 13 to process the jackpot.

If the player 24 wants to collect the jackpot, the user 54, via theremote device 50A, requests a jackpot form (not shown). The remotenetwork interface 68 sends the jackpot form to the remote device 50A.

When the user 54 selects the jackpot form from the menu layer 80, theweb client 56 relays the request to the remote network interface 68. Theremote network interface 68 retrieves the jackpot form and sends thejackpot form to the remote device 50A for display and interaction withthe user 54 via the web client 56.

The jackpot form includes a jackpot button for selecting by the user 54to communicate each step of the jackpot processing that has occurred.For example, the jackpot button is a request button that the user 54selects when a jackpot is announced and the user 54 is approached by theplayer 24 to collect the jackpot. The jackpot button may be anacknowledge button selected by the user 54 after validating the jackpotand prior to processing the jackpot. The jackpot button may also be aprocess button selected by the user 54 after confirming that the jackpotmay be paid. The jackpot button may also be a paid button to confirmthat the user 54 has paid to the player 24 the value of the jackpot.Each time the jackpot button is selected by the user 54, the remotedevice 50A sends a notification of the event and the remote networkinterface 68 stores the notification in the host computer 18 which thenupdates the data in the database 22 relating to the jackpot status inthe jackpot processing.

In one embodiment, the jackpot form lists several fields having jackpotinformation, including the jackpot identifier, fill detail and jackpotstatus, for all active jackpots. The user 54 may select either thejackpot identifier or the jackpot status. If the user 54 selects thejackpot identifier, then jackpot detail is displayed on the remotedevice 50A. If the user 54 selects jackpot status, then the jackpotstatus advances to an advanced jackpot status, a notification is sent tothe host computer 18 to update the database 22 and the remote device 50Adisplays the updated jackpot status on the jackpot form.

In another embodiment, the jackpot form includes a field wherein theuser 54 enters the jackpot id such as a number. The user 54 entersjackpot information or data onto the remote device 50A to verify thatthe jackpot is valid and has not been previously processed. If thejackpot id is invalid or the jackpot has already been processed, anerror message is displayed at the remote device 50A. The jackpotinformation is sent by the remote device 50A to the host computer 18where jackpot information is retrieved and sent back to the remotedevice 50A.

In one embodiment, the jackpot id is entered manually, then the user 54selects a jackpot entry button to send the jackpot form to the hostcomputer 18. In another embodiment, the jackpot id is read by the barcode reader and sent to the host computer 18.

In one embodiment, the user 54 navigates to a servlet 24 using the menulayer 80 for inputting and retrieving jackpot information. The menulayer 80 requests the servlet from the host computer 18 from which it isthen downloaded to the remote device 50A.

After the validity of jackpot is confirmed, the jackpot information isretrieved from the database 22 by the remote network interface 68 anddisplayed to the user 54 at the remote device 50A. With specificreference to FIG. 14A, in one embodiment the returned jackpotinformation is displayed on the remote device 50A in a jackpotinformation screen 238. With reference to FIG. 14B, in anotherembodiment, the returned fill information is displayed on the remotedevice 50A in a fill information screen 240.

The jackpot information includes fill detail 198, such as a gamingmachine identifier. The gaming machine identifier includes a gamingmachine id and a gaming machine location to identify the gaming machineissuing the jackpot. The fill detail 198 further includes a gaming datefor identifying the issue date of the jackpot, a gaming shift foridentifying the work shift during which the jackpot was issued, and ajackpot value for identifying the value of the jackpot, thereby allowingthe user 54 to confirm the value printed on the jackpot and the valuestored in the host computer 18.

If the user 54 selects the jackpot identifier field on the jackpot form,jackpot detail 200 as a function of the jackpot identifier is retrievedfrom the host computer 18 and displayed at the remote device 50A.Jackpot detail 200 may include the gaming machine id and the gamingmachine location to identify the gaming machine issuing the jackpot. Thejackpot detail 200 may further include a gaming machine name foridentifying the particular game issuing the jackpot, a gamingdenomination for identifying the particular type of credit issued, thegaming date for identifying the issue date of the jackpot, and thegaming shift for identifying the work shift during which the jackpot wasissued.

With specific reference to FIG. 13A, a first method 202 for processing ajackpot using the remote device 50A, according to a first embodiment ofthe present invention is shown. In a first step 204, a selectablejackpot form is sent to the remote device 50A. In a second step 206, thejackpot information is entered on the jackpot form via the remote device50A.

With specific reference to FIG. 13B, in another aspect of the presentinvention, a method 208 for displaying or processing jackpots is shown.In a first step 210, all pending jackpots are displayed. In oneembodiment, the list of pending jackpots includes at least a jackpot idand a jackpot status. In a second step 214, if the user 54 selectsjackpot id of a jackpot, the method 208 proceeds to a third step 222. Ifthe user 54 selects the jackpot status, the method 208 proceeds to afourth step 236. In the third step 222, jackpot details are displayed onthe remote device 50A. In the fourth step 236, the selected jackpot isprocessed by the user 54.

F. Remote Hopper Fill Ticket Processing

With reference to FIGS. 15A, 15B, 16A and 16B, the remote system 48allows the user 54, such as a slot floor employee to quickly andremotely process a hopper fills in a particular gaming machine 13, i.e.,insert credits or coins into the game machine's hopper to be dispensedto the player 24 when a jackpot has been won, when the game machine hasrun out or is low on credits. The number of credits remaining in thehopper (not shown) are tracked by the host computer 18 (or game machine13 and relayed to the host computer)which issues an alert when thenumber of credits remaining reaches a certain amount so that the hoppermay be restocked with credits such as coins, tokens, paper money, or thelike.

Once an alert is issued, the user 54, via the remote device 50A, mayacknowledge the alert and request a hopper fill form (not shown). Theremote network interface 68 sends the hopper fill form to the remotedevice 50A.

When the user 54 selects the hopper fill form from the menu layer 80,the web client 56 relays the request to the remote network interface 68.The remote network interface 68 retrieves the hopper fill form and sendsthe hopper fill form to the remote device 50A for display andinteraction with the user 54 via the web client 56.

In one embodiment, the hopper fill form includes a hopper fill button(not shown) for selecting by the user 54 to communicate each step of thehopper fill processing that has occurred. For example, the hopper fillbutton is a request button that the user 54 selects when an alert isannounced and the user 54 approaches the gaming machine 13 to processthe hopper fill. The hopper fill button may also be an acknowledgebutton selected by the user 54 after validating the hopper fill andprior to processing the hopper fill. The hopper fill button may also bea process button selected by the user 54 after confirming that thehopper is being restocked. The hopper fill button may also be a fillbutton to confirm that the user 54 has completed restocking the hopper.Each time the hopper fill button is selected by the user, the remotedevice 50A sends a notification of the event and the remote interfacestores the notification in the host computer 18 which then updates thedata in the database 22 relating to the credit status in the hopper fillprocessing.

In one embodiment, the hopper fill form lists several fields havinghopper fill information, including the hopper fill identifier, filldetail and credit status, for all active hopper fills. The user 54 mayselect either the hopper fill identifier or the credit status. If theuser 54 selects the hopper fill identifier, then hopper fill detail isdisplayed on the remote device 50A. If the user 54 selects creditstatus, then the credit status advances to an advanced credit status, anotification is sent to the host computer to update the database and theremote device displays the updated credit status on the hopper fillform.

In another embodiment, the hopper fill includes a field wherein the user54 enters the hopper id, such as a number. The user 54 enters hopperfill information or data onto the remote device 50A to verify that thehopper id is valid and has not been previously processed. If the hopperid is invalid or the hopper fill has already been processed, an errormessage is displayed at the remote device 50A. The entered hopper fillinformation is sent by the remote device 50A to the host computer 18where additional hopper fill information is retrieved and sent back tothe remote device 50A. In one embodiment, the hopper id is enteredmanually, then the user 54 selects a hopper fill entry button to sendthe hopper fill form to the host computer 18. In another embodiment, thehopper id is read from a barcode on the hopper or on the game machine 13by the bar code reader 66 and sent to the host computer 18.

In one embodiment, the user 54 navigates to a servlet 24 using the menulayer 80 for inputting and retrieving hopper fill information. The menulayer 80 requests the servlet from the host computer 18 from which it isthen downloaded to the remote device 50A.

After the validity of hopper is confirmed, the hopper fill informationis retrieved from the database 22 by the remote network interface 68 anddisplayed to the user 54 at the remote device 50A. With specificreference to FIG. 16A, in one embodiment the returned hopper fillinformation is displayed on the remote device 50A in a hopper fillinformation screen 288. With reference to FIG. 16B, in anotherembodiment, the returned fill information is displayed on the remotedevice 50A in a fill information screen 290.

The hopper fill information includes fill detail 248, such as a gamingmachine identifier. The gaming machine identifier includes a gamingmachine id and a gaming machine location to identify the gaming machinerequiring the hopper fill. The fill detail 248 may further include agaming date for identifying the issue date of the fill, a gaming shiftfor identifying the work shift during which the fill was issued, and/ora credit value for identifying the value of the credits supplied.

If the user 54 selects the hopper fill identifier field on the hopperfill form, hopper fill detail as a function of the hopper fillidentifier is retrieved from the host computer 18 and displayed at theremote device 50A. In one embodiment, the hopper fill detail includesthe gaming machine id and the gaming machine location to identify thegaming machine requiring the credit or hopper fill. The hopper filldetail may further include a gaming machine game for identifying theparticular game issuing the credits, a gaming denomination foridentifying the particular type of credit issued, the gaming date foridentifying the fill date of the hopper, and/or the gaming shift foridentifying the work shift during which the hopper was filled.

With specific reference to FIG. 15A, a first method 252 for processing ahopper fill using the remote device 50A, according to a first embodimentof the present invention is shown. In a first step 254, a selectablehopper fill form is sent to the remote device 50A. In a second step 256,the hopper fill information is entered on the hopper fill form via theremote device 50A.

With specific reference to FIG. 15B, a second method 258 for processingthe hopper fill using the remote device 50A, according to a secondembodiment of the present invention is shown.

In a first step 260, the remote device 50A displays selectable hopperfill information, including pending fills having a credit status andhopper fill identifier. In an alternate embodiment, the hopper fill formor gaming machines 13 having hopper fill information, is displayed onthe remote device 50A. In one embodiment, the hopper fill information isselectable. In another embodiment the hopper fill information isfillable requiring credit refill.

In a second step 262, the user 54 selects a pending fill. If the user 54selects the hopper fill identifier, control proceeds to a third step264, the fill detail is displayed and control returns to the first step260. If the user 54 selects the credit status, then the credit statusadvances to an advanced credit status and control returns to the firststep 260. If all required information was not entered, then an errormessage is displayed and the hopper fill form is displayed again.

Then he hopper id is verified. If the hopper id is not valid, then themethod 258 displays an error message (fourth step 266). If the hopper idis valid, then the fill detail is retrieved from the database 22 anddisplayed at the remote device 50A.

After the hopper is filled with credits by the user 54, the remotedisplay displays a credit filled message.

If the user selects another hopper fill identifier, the hopper filldetail is retrieved from the host computer and displayed on the remotedevice 50A.

If the user selects a credit status, the credit status advances to anadvanced credit status which is then displayed at the remote device 50A.

G. Remote Table Rating Interface

With reference to FIGS. 17A, 17B, and 18, the remote system 48 allowsthe user 54, such as a slot floor employee or patron host, to quicklyand remotely process a table rating and, send and receive table ratinginformation 450 related to a specific player 24. A table rating allowsthe gaming system 10 to rate or rank the player 24 by determining his orher given session or play, determine his or her worth to the casino, andassign a point award.

In the illustrated embodiment, interaction with the user 54, includingreceiving input and displaying the player information, is accomplishedusing the web client 56.

In one aspect of the present invention, the user 54 may identify theplayer 24 through entry of the player's ID card number into the remotedevice 50A. In one embodiment, the ID card number may be enteredmanually. In another embodiment, the ID card number may be read from theplayer's ID card using the card reader 62 or the barcode reader 66 asappropriate.

In another aspect of the present invention, if the player 24 isutilizing one of the devices 12 and has identified themselves to thegaming system by entry of the ID card into the device 12 and/or enteredin their PIN number, the user 54 may identify the player 24 by enteringa device ID number associated with the respective device 12. Asdiscussed below, the gaming system has associated the ID number of thedevice 12 with the player 24 while the player 24 is using the device 12.Thus, using the device ID number, the host computer 18 may determine theID number of the player 24.

In one embodiment, the user 54 navigates to a servlet for requestingplayer information using the menu layer 80. The menu layer 80 requeststhe servlet from the host computer 18 from which it is then downloadedto the remote device 50A.

The servlet displays a table rating form which is displayed to the user54. As discussed above, the user 54 may either enter the player ID cardnumber of the player 24 (manually or reading it from the ID card) or adevice ID number associated with a device 12 being used by the player24. The user 54 enters the player information (in the form of the playerID card number or the device ID number) which is returned to the hostcomputer 18 by the web client 56. The remote network interface 68receives the player information, retrieves the table rating information450 and returns the table rating information 450 to the remote device50A where it is displayed. With specific reference to FIG. 18, in oneembodiment the returned table rating information is displayed on theremote device 50A in an open table rating form screen 486.

When the player information is entered, the remote network interface 68determines whether the information is valid. If valid, the table ratinginformation 450 is stored in or retrieved from the database 22 as afunction of the identification information. If invalid, an error messageis displayed on the remote device 50A. The player information 450includes a player identifier such as a player number, player name andaddress, and the like.

The purpose of the table rating information 450 is to register anddisplay a patron's risk or ranking at a particular gaming machine. Therisk or ranking informs the user 54 about the player's 24 spending orrisk habits during a given session of play at a gaming machine.

The player information includes a table rating status of open or closedfor a particular gaming machine 13. If the status is open, the player iscurrently playing the particular gaming machine 13, thereby enabling theuser to generate a table rating. When the player 24 decides todiscontinue playing, the user 54 swipes the player's 24 ID card andbrings up the table rating status in a closed status form (not shown)having fillable fields and a status button. The user 54 enters tablerating information about the session, including but not limited to theplayer name, the gaming machine 13, the gaming machine location, thetime the player 24 began play, the time the player 24 ceased play, theaverage bet by the player 24, and the amount won by the player 24 whenleaving the gaming machine 13. The user 54 selects the status button andthe table rating is established, sent to the database via the remotenetwork interface and stored therein. Thereafter, any remote devicesdisplaying a table rating form relating to the particular gaming machine13 displays the newly entered table rating information.

If, after swiping the player's card, the player 24 does not have an opentable rating, an open table form is displayed on the remote device. Theopen table form is fillable by the user 54 with table rating detailswhich may include the player's name, the zone information (gamingmachine location), a selectable list of the bank information (gamingmachines 13) available at that location, a seat identifier at which theplayer 24 is seated, the estimated average bet by the player 24, the betvalue the player is opening the gaming machine 13 with. The zoneinformation entered by the user 54 may also include bank information asa function of the zone information. The bank information associated withthe zone information is displayed and the user 54 selects theappropriate banking information associated with the particular gamingmachine 13.

Once the information is entered, the user 54 selects the status buttonto send and store the table rating details to the database 22 and updatethe table rating status to open. The updated table rating status is sentto all remote devices displaying information for the particular gamingtable. The update may be sent automatically or upon request.

With specific reference to FIG. 17A, a first method 452 for remotelyrequesting table rating information relating to a player 24 is provided.In a first step 454, a fillable form is sent to a remote device forreceiving table rating information. In a second step 456, the tablerating information is received at the host computer for processing atable rating for the player.

With specific reference to FIG. 17B, a second method 458 for remotelyprocessing a table rating using the remote device 50A is shown,according to a second embodiment of the present invention.

In a first step 460, the table rating form is displayed on the remotedevice 50A.

In a second step, if a player ID card number is entered, then the methodproceeds to a third step. The table rating status is then returned tothe remote device 50A to be displayed in the third step 464.

In a fourth step 466, if the table rating status is open, the closedstatus form is displayed on the remote device.

In a fifth step 468, t the table rating is closed and control returns tothe first step 460. In the third step 464, if the table rating status isnot open, then the method 458 proceeds to a sixth step 470.

In the sixth step 470, the system determines if the remote networkinterface is a casino. System view shows the zones of the system andcontrol proceeds to a seventh step 472. If the system view shows thezones then control proceeds to a seventh step 472, otherwise controlproceeds to a ninth step 476.

In the seventh step 472, zone information is displayed.

In an eighth step 474, zone is selected and control proceeds to theninth step 476.

In the ninth step 476, the system determines if the remote networkinterface shows the zone view and control proceeds to a tenth step 478.

If the system shows the zone view, then bank information is shown in thetenth step 478 and control proceeds to an eleventh step 480. Otherwise,control proceeds to a twelfth step 482.

In the eleventh step 480, a bank is entered, and control proceeds to thetwelfth step 482.

In the twelfth step 482, the open rating form is displayed and controlproceeds to a thirteenth step 484.

In the thirteenth step 484, the user 54 enters table rating information.

In the fourteenth step 486, the table rating is opened and controlreturns to the first step 460.

H. Remote Attendance

With reference to FIGS. 19A, 19B, and 20, the remote system 48 allowsthe user 54, such as a slot floor employee or patron host, to quicklyand remotely request, send and receive player attendance information 350related to a specific player 24. For example, a marketing or specialevent may be targeted to patrons or players meeting defined criteria.Each player who attends the event is identified as their attendance isstored in the player tracking system.

In the illustrated embodiment, interaction with the user 54, includingreceiving input and displaying the player attendance information, isaccomplished using the web client 56.

In one aspect of the present invention, the user 54 may identify theplayer 24 through entry of the player's ID card number into the remotedevice 50A. In one embodiment, the ID card number may be enteredmanually. In another embodiment, the ID card number may be read from theplayer's ID card using the card reader 62 or the barcode reader 66 asappropriate.

In another aspect of the present invention, if the player 24 isutilizing one of the devices 12 and has identified themselves to thegaming system by entry of the ID card into the device 12 and/or enteredin their PIN number, the user 54 may identify the player 24 by enteringa device ID number associated with the respective device 12. Asdiscussed below, the gaming system has associated the ID number of thedevice 12 with the player 24 while the player 24 is using the device 12.Thus, using the device ID number, the host computer 18 may determine theID number of the player 24.

In one embodiment, the user 54 navigates to a servlet for requestingplayer attendance information using the menu layer 80. The menu layer 80requests the servlet from the host computer 18 from which it is thendownloaded to the remote device 50A.

The servlet displays an attendance form which is displayed to the user54. As discussed above, the user 54 may either enter the player ID cardnumber of the player 24 (manually or reading it from the ID card) or adevice ID number associated with a device 12 being used by the player24. The user 54 enters identification information (in the form of theplayer ID card number or the device ID number) which is returned to thehost computer 18 by the web client 56. The remote network interface 68receives the identification information, retrieves the player attendanceinformation 350 and returns the player attendance information 350 to theremote device 50A where it is displayed. With specific reference to FIG.20, in one embodiment the returned player attendance information isdisplayed on the remote device 50A in an player attendance informationscreen 384.

When the identification information is entered, the remote networkinterface 68 determines whether the identification is valid. If valid,the gaming machine information is stored in or retrieved from thedatabase 22 as a function of the identification information. If invalid,an error message is displayed on the remote device. 50A. The gamingmachine information includes a device identification number, and theplayer attendance information is retrieved from the database 22 as afunction of the device identification number. The player attendanceinformation 350 includes a player identifier such as a player number,player name and address, and the like. The player attendance information350 includes a gaming machine identifier which indicates what gamingmachines the player 24 has attended on a particular day.

The purpose of the player attendance information 350 is to register anddisplay a patrons attendance at a particular gaming machine or marketingevent. Attempting to register a player 24 already registered willgenerate and display an error.

With specific reference to FIG. 19A, a first method 352 for remotelyrequesting information relating to a player 24 is provided. In a firststep 354, identification information is received at the remote device.In a second step 356, the identification information is received at thehost computer. In a third step 358, identification information is storedin the database, i.e., the player before is marked as the playerattending the event. In a fourth step 360, the player attendanceinformation is retrieved from the database 22 as a function of theidentification information.

With specific reference to FIG. 19B, a second method 362 for remotelyrequesting player information using the remote device 50A is shown,according to a second embodiment of the present invention.

In a first step 364, the attendance form is requested by the user 54 onthe remote device 50A.

In a second step 366, the user 54 selects and enters an event or gamingvia machine and control proceeds to a fourth step 370.

In a third step 368, an error message is displayed if the user does notenter or select an event and control returns to the first step 364.

In the fourth step 370, if a player ID card number is entered, then themethod 362 proceeds to a fifth step 372.

In the fifth step 372, the ID card number is validated.

In a sixth step 374, if system determines if the ID card number is notvalid, and control proceeds to the third step 368 where an error messageis displayed. If the ID card number is valid, then the method proceedsto a seventh step 376.

In the seventh step 376, if the player 24 is not marked as attending theevent, the control proceeds to an eighth step 378.

In the eight step 378, the player's attendance at the gaming machine isregistered by the system, and control returns to the first step 264.

I. Remote Surveillance

With reference to FIGS. 21A, 21B, and 22, the remote system 48 allowsthe user 54, such as a slot floor employee or patron host to quickly andremotely process an alert having data including user role information,alert information and alert detail issued by a gaming machine 13. Theuser role information is a system where each user 54 is assigned a rolein a hierarchy of roles. The user's role and level on the hierarchydetermines which functions and information the user can access and theoperations the user can perform.

In the illustrated embodiment, interaction with the user 54, includingreceiving input and displaying the alert information, is accomplishedusing the web client 56.

In one aspect of the present invention, an alert form displays allactive alerts and displays the alerts on the remote device 50A in analert form as a function of the user role information. The alert formdisplays the alert and the date and time it occurred. The user 54 mayidentify the alert and select the alert via an alert button toacknowledge that the user 54 is addressing the alert and will clear thealert after it is addressed. After the user 54 addresses the alert andacknowledges that it is addressed, the database 22 is updated and thealert form is refreshed with updated alert information.

In the illustrated embodiment, the user 54 selects the alert from thealert form and alert details 300 are displayed. The alert details mayinclude, but are not limited to, an alert type for describing the alertand an alert date for describing the date and time that the alertoccurred. The alert details 300 may further include a device identifierfor describing the gaming device the alert occurred on, a zone name fordescribing the zone of the gaming floor that the device is located in,and a bank name for describing the bank of the gaming floor that thedevice is located in. Additional alert details 300 may include arepository identifier for describing the repository the alert occurredon, a document identifier for describing a document created by thealert, an alert value for describing the value of the alert, and analert point describing the point value of the alert. The alert details300 may also further include an employee identifier for describing theemployee that initiated the alert and an alert message providing a textdescription of the alert.

In one embodiment, the user 54 navigates to a servlet for requestingalert information using the menu layer 80. The menu layer 80 requeststhe servlet from the host computer 18 from which it is then downloadedto the remote device 50A.

In one embodiment, the servlet displays the alert form which isdisplayed to the user 54. As discussed above, the user 54 may select thealert displayed on the alert form to retrieve the alert detail 300 whichis returned to the host computer 18 by the web client 56. The remotenetwork interface 68 receives the alert information, retrieves the alertdetail 300 and returns the alert detail 300 to the remote device 50Awhere it is displayed. With specific reference to FIG. 22, in oneembodiment the returned alert information is displayed on the remotedevice 50A in an alert information screen 330.

With specific reference to FIG. 21A, a first method 302 for remotelyprocessing an alert is provided. In a first step 304, alert informationis received at the remote device. In a second step 306, the user selectsthe alert. In a third step 308, the alert information is retrieved fromthe database 22 as a function of the selected alert.

With specific reference to FIG. 21B, a second method 310 for remotelyrequesting player information using the remote device 50A is shown,according to a second embodiment of the present invention.

In a first step 312, the alert information is retrieved as a function ofthe user role.

In a second step 314, the retrieved alert information is displayed onthe remote device 50A.

In a third step 316, the user selects an alert, then the method 310proceeds to a fourth step 318.

In the fourth step 318, alert detail is retrieved and displayed as afunction of the selected alert.

In a fifth step 320, the user selects an alert button for refreshing thealert information stored in the system 10.

In a sixth step 322, the user acknowledges the alert.

In a seventh step324, the system determines if the alert has alreadybeen acknowledged.

In an eighth step 326, if the alert was previously acknowledged, anerror message is displayed and the method returns to the first step 312.If the acknowledgement is valid, then the message proceeds to the ninthstep 328.

In the ninth step 328, the alert is processed by the host computer 18,notification is sent to other processes in the system, including thedatabase and control returns to the first step 312.

In the third step 316, the user selects the alert button to refresh thealert information displayed at the remote device 50A.

Obviously, many modifications and variations of the present inventionare possible in light of the above teachings. The invention may bepracticed otherwise than as specifically described within the scope ofthe appended claims.

J. Patron Point Adjustment

With reference to FIGS. 23A, 23B and 24, the remote devices 50 allow auser 54 to display and/or increase a player's point, e.g., bonus points,or comp point balance. In one embodiment, the remote network interface68 exchanges data between the host computer 18 and the remoter device50. The data includes adjustment information to adjust the pointsassociated with a player 24 in the player tracking system.

In one embodiment, the data includes a point management form (not shown)which is sent from the remote network interface 68 to the remote device50A. The point management form is fillable with player information bythe user 54. The remote device 50 sends the player information to theremote network interface 68. Once the player 24 has been identified, theremote network interface 68 sends a point adjustment request from to theremote device 50A.

With specific reference to FIG. 24, a sample point adjustment requestform 506, according to one embodiment, is shown. In the illustratedembodiment, the point adjustment request form allows the user 54 toenter the type of points, the number of points, the reason for theadjustment, and the player ID card number associated with the player 54.When finished, the user 54 may select an ISSUE button to send the dateto the host computer is where the database 22 is updated.

With specific reference to FIG. 23B, a second method 510 for adjustingpoints associated with a player 24 in a player tracking system is shown.In a first step 512, a request is displayed on the remote device 50A.The user 54 may then fill out the form and send the form back to thehost computer 18. In one embodiment, a player I) card number is manuallyentered on the remote device 59A. In another embodiment, the player IDcard number is read from the ID card by the bar code reader 66 or the IDcard reader 62.

In a second step 514, if a card number was entered, then the method 510proceeds to a third step 516. If a card number was not entered, then themethod 510 proceeds to a fourth step 516 and an error message isdisplayed. In the third step 516, the card number is validated. In afifth step 518, if the card number is valid then the method 510 proceedsto a sixth step 520. In the sixth step 520, approval for the requestedtransaction is processed. In a seventh step 522 if the user or employee54 has the necessary rights to adjust the player or patron's points thenthe method 512 proceeds to an eighth step 524. Otherwise, the methodproceeds to the fourth step 516 and an error message is displayed. Inthe eighth step 524, the points are adjusted and the process returns thefirst step 512.

K. Comp Point Vouchers

With reference to FIGS. 25A, 25B and 26, the remote device 50 may beused to issue point vouchers or comp point vouchers to a player 24. Thevouchers may be embodied in a paper voucher which is printed on a remoteprinter carried by the user 54 or may be embodied in a pre-printedvoucher having a voucher ID number which is carried by the user 54, andassigned to the player 24 in the player tracking system. Alternatively,the voucher may be embodied in a record stored in the database 22.

In one embodiment of the present invention, the remote network interface68 exchanges data between the host computer 18 and the remote device50A. The data includes voucher information to issue a voucher to theplayer 24 in the player tracking system. The voucher has at least one ofan associated product and service. For example, the voucher may beredeemed for the associated product at a related retail store orredeemed for the associated service. Exemplary products includes freedinners and/or drinks.

As discussed below the remote network interface 68 may send a requestform to the remote device 50A. The user 54 enters data onto the requestform and the remote device sends the data to the remote networkinterface 68.

With specific reference to FIG. 25, in one embodiment of the presentinvention, a method 530 implements a player tracking system for use withthe gaming system. In a first step 532 a fillable form is sent to theremote device 50A. In a second step 534, the form is filled with datafor issuing a voucher to the player 24.

The user 54 may enter the player ID card number associated with theplayer 24 on the request form. In one embodiment, the player ID cardnumber is entered manually. In another embodiment, the player ID card isread from the player ID card by the ID card reader 62 or the bar codereader 66. After the player has been identified, a list of the vouchersfor which the patron has enough comp points to purchase are listed. Withspecific reference to FIG. 26, a player voucher form 536, according toan embodiment of the present invention, is shown. The player voucherform 536 displays the patron name, the player ID card number, the typeof voucher being selected and the points associated with the patron inthe player tracking system. The player voucher form 536 also lists thevouchers for which the patron may purchase based on the number of comppoints they have.

With specific reference to FIG. 25B, a flow diagram of a second method536 for assigning vouchers to a player in a player tracking system isshown. In a first step 540, a first request form is displayed on theremote device 50A. The first request form allows the user 54 to selectthe type of voucher, i.e., either point or comp point and to enter thecard number of the player or patron 24. In a second step 542, if a cardnumber was entered then the process proceeds to a third step 546.Otherwise, the method 538 proceeds to a fourth step 544 and an errormessage is displayed. In the third step 546, the player's ID card numberis validated. In a fourth step 548, if the ID card number is valid, thenthe method 538 proceeds to a fifth step 550. Otherwise, the method 538proceeds to the third step 544 and an error message is displayed. In thefifth step 550, if the player 24 has any points in the player trackingsystem, then the method 538 proceeds to a sixth step 552. Otherwise, themethod 538 proceeds to the third step 544 and an error message isdisplayed. In the sixth step 552, if there are any active comps orvouchers that the player 24 can afford based on the number of pointsassociated with the player 24 in the patron tracking system, then themethod 538 proceeds to the seventh step 554. Otherwise, the methodproceeds to the third step 544 and an error message is displayed. In theseventh step 554, a request form or player voucher form 548 is displayedon the remote device 50A. As discussed above, the player voucher form548 displays a list of vouchers that the player can afford. If the user54 selects one of the vouchers and selects the issue button, then thevoucher or comps are issued in the eighth step 556. In a ninth step 558,if the comp or voucher was issued without errors then the method returnsto the first step 540. Otherwise, the method returns to the third step544 and an error message is displayed.

L. Redemption of Printed Vouchers

With reference to FIGS. 27A, 27B and 28, the remote device 50 may beused to validated and process, i.e., redeem, printed vouchers. A printervoucher may be distributed for any number of reasons, for example,including a promotional event. Typically, the voucher may be redeemedfor an associated service or product. For example, a printer voucher maybe redeemed for a free dinner or drink.

As discussed below in one embodiment, the remote network interface 68generates and delivers to the remote device 50A a request form. The user54 may enter a voucher ID number onto the form. By pressing a continuebutton, the voucher ID may be validated and processed. A status may thenbe returned to the user 54.

With reference to FIG. 27A, in one embodiment a method 540 is used toredeem a voucher. In a first step 542, a fillable form is sent to theremote device 50A. In a second step 544, the fillable form is filled outwithout voucher information by the user 54A. In one embodiment, thevoucher information includes a voucher ID number which may be enteredmanually or by reading a code on the voucher. For example, the code maybe a bar code printed on the voucher which is read by the bar codereader 66. In a third step 546, the voucher ID number is validated andredeemed.

With specific reference to FIG. 28, in one embodiment, once a voucherhas been identified by the remote network interface 68, a voucherinformation form 548 is displayed on the remote device 50A. The voucherinformation form 548 in the illustrated embodiment includes the voucherID number, a good for field which identifies the product or service forwhich the voucher may be redeemed, an issued date, and an expirationdate. Once the user 54 verifies the data displayed on the voucherinformation form, the user 54 may press the continue button to validateand except the voucher.

With specific reference to FIG. 27B, a method 550 for validating andprocessing and redeeming printed vouchers according to anotherembodiment of the present invention is shown. In a first step 552, arequest form is displayed on the remote device 50A. The request formallows the user 54 to enter a voucher number or a voucher ID number. Inone embodiment, the voucher ID number is entered manually. In anotherembodiment, the voucher number is read from the printed voucher. Forexample, the voucher ID number may be encoded into a bar code which isread by the bar code reader 66. In a second step 554, if the voucher IDnumber has been entered then the method proceeds to a third step 556.Otherwise, the method 550 proceeds to a fourth step 558 and an errormessage is displayed. In the third step 556, the voucher number isvalidated. In a fifth step 560, if the voucher number is valid, then themethod proceeds to a sixth step 562. Otherwise, the method proceeds tothe fourth step 558 and an error message is displayed. In the sixth step562, if the voucher has already or previously been accepted, then themethod 550 proceeds to the fourth method step 558 and an error messageis displayed. Otherwise, the method 550 proceeds to a seventh methodstep 564 and the voucher is marked as accepted within the database 22.

M. Voucher Information Retrieval

With reference to FIGS. 29A, 29B and 30, the remote device 50A may beused to display a list of outstanding vouchers for a selected player orpatron 24 and allow the user 54 to accept a specific voucher. Typicallythe voucher has an associated good, i.e., product, or service for whichit may be redeemed. For example, a specific voucher may be redeemed fora free dinner and/or drink. In one embodiment, each voucher has a uniquevoucher ID number and is stored as a record in the database 22. Inanother embodiment, the voucher may be embodied in a printed tickethaving the voucher ID printed or encoded thereon. The voucher ID numberwould be associated with the player 24 in the database 22.

In one aspect of the present invention, at least one voucher is assignedto the player 24 in the player tracking system. The voucher has at leastone of the good and/or service for which it may be exchanged. The remotenetwork interface 68 may be used for exchanging data between the hostcomputer 18 and the remote device 50A. The data includes voucherinformation associated with the voucher assigned to the player 24 in theplayer tracking system.

In one embodiment, the data exchange between the remote device 50A andthe remote network interface 68 includes a request form. The remotenetwork interface 68 sends the request form to the remote device 50A.The request form may be used by the user 54 for entering informationrelated to the player. The remote device 50A sends the playerinformation to the remote interface 68. As discussed below, in oneembodiment of the present invention, the player information includes theplayer ID card number. The player ID card number may be entered manuallyor may be read by the player ID card reader 62 or the bar code reader66, as appropriate. The player ID card number is relayed to the remotenetwork interface 68. The remote network interface 68 returns a list ofoutstanding vouchers associated with the player 24. The user 54 may viewdetails related to each voucher. The user 54 may select one of thevouchers to accept, i.e., redeem for the associated service or good.

With specific reference to FIG. 29A, a first method 570 for redeemingoutstanding vouchers for a selected player 24 is shown. In a first step572, a fillable form is sent to the remote device 50A. In a second step574, the form is filled out by the user 54 for identifying the player.In a third step 576, voucher information is retrieved through the remotenetwork interface 68. As discussed above, once the player has beenidentified, a list of outstanding vouchers is returned to the remotedevice 50A. A details button (not shown) associated with each voucher inthe list may be selected by the user 54 to display voucher informationrelated to the selected voucher. For example, with reference to FIG. 30,an exemplary voucher information screen 578 is shown. The voucherinformation screen 578 may display the voucher ID number, the good orservice for which it may be redeemed, the date it was issued, and thedate the voucher expires. The voucher information screen 578 alsoincludes an accept button which may be selected by the user to acceptthe voucher as it is redeemed.

With specific reference to FIG. 29B, second method 580 for displayingand redeeming outstanding vouchers associated with the player 24 isshown. In a first step 582, a request form is displayed on the remotedevice 50A. In one embodiment, the user 54 may enter a player ID cardnumber on the request form. In one embodiment, the player ID card numberis entered manually. In another embodiment, the player ID card numbermay be read from the player ID card by the ID card reader 62 or the barcode reader 66. In a second step 584, if an ID card number has beenentered, then the method 580 proceeds to a third step 588. Otherwise,the method 580 proceeds to a fourth step 586 and an error message isdisplayed. In the third step 588, the ID card number is validated. In afifth step 590, if the ID card number is not valid, then the method 580proceeds to the third step 586 and an error message is displayed.Otherwise, the method proceeds to a sixth step 592.

In the sixth step 592, if the player 24 does not have any outstandingvouchers, then the method 580 proceeds to the fourth step 586 and anerror message is displayed. Otherwise, the method 580 proceeds to aseventh step 594.

In the seventh step 594, any outstanding vouchers associated with theplayer 24 are retrieved from the database 22. In an eighth step 596, theretrieved outstanding vouchers are displayed on the remote device 50A.As discussed above, each voucher in the list has an associated detailbutton (not shown).

In a ninth step 598, if the detail button for one of the listed voucherswas pressed or selected, then the method 580 proceeds to a tenth step600. Otherwise, the method 580 returns to the first step 592. In thetenth step 600, voucher details for the selected voucher are retrievedfrom the database 22. In eleventh step 602, the voucher details for theselected voucher are displayed on the remote device 50A. In a twelfthstep 604, if the accept button for the selected voucher was pressed orselected, then the method 580 proceeds to a thirteenth step 606.Otherwise, the method 580 returns to the seventh step 594.

In the thirteenth step 606, the selected voucher is marked as beingaccepted and the method returns to the seventh step 594.

N. System Information

In another aspect of the present invention, the database 22 may storeinformation related to the remote devices 50, including the currentstate of the remote device 50. As discussed below, this information maybe retrieved and displayed on the remote device 50A, for example, forpurposes of tech support. In one embodiment, the user 54 selects theservlet or applet from the menu layer 80. The remote network interface68 produces an HTML form that displays the information related to theremote device 50 to the user 54.

In one embodiment, the data includes information which is associatedwith a current client being utilized on the remote device 50A. Forexample, the data may include but is not limited to a TCP/IP address ofthe current client. An HTTP context of the current client for thecurrent session, an IOP ID of the current client as defined in thedatabase 22 and an IOP name of the current client is defined in thedatabase. IOP or input output point is a designator to represent a pointof data input or output such as a dedicated terminal, hand held device,etc., that is distinguished usually by its IP address on the network.The IOP ID and name are used to tie transactions that are generated to aparticular entity or device.

The data may also include information related to a current user 54 ofthe remote device 50. For example, the data may include an employee IDnumber and/or the employee name.

Obviously, many modifications and variations of the present inventionare possible in light of the above teachings. The invention may bepracticed otherwise than as specifically described within the scope ofthe appended claims.

1. A remote system for use with a gaming system, the gaming system forimplementing a player tracking system for tracking points, the remotesystem comprising: a remote device; and, a remote network interfacecoupled to the remote device for exchanging data between a host computerand the remote device, the data including adjustment information toadjust the points associated with a player in the player trackingsystem.
 2. A remote system, as set forth in claim 1, wherein the remotedevice is coupled to the remote network interface by a wirelessconnection.
 3. A remote system, as set forth in claim 2, wherein thewireless connection uses an IEEE 802.11 standard.
 4. A remote system, asset forth in claim 3, wherein the wireless connection is IEEE 802.11b.5. A remote system, as set forth in claim 3, wherein the wirelessconnection is IEEE 802.11g.
 6. A remote system, as set forth in claim 1,the remote device having a processor and a web client for interactionwith a user.
 7. A remote system, as set forth in claim 6, the web clientfor acquiring input from the user and formatting and presenting data tothe user.
 8. A remote system, as set forth in claim 1, the dataincluding a point management form, the remote network interface forsending the point management form to the remote device.
 9. A remotesystem, as set forth in claim 8, the data including player information,the point management form being fillable with the player information bya user, the remote device for sending the player information to theremote network interface.
 10. A remote system, as set forth in claim 9,the remote device having a processor and a web client for interactionwith a user, the point management form being accessible through the webclient.
 11. A remote system, as set forth in claim 10, the remotenetwork interface for confirming that all required information on thepoint management form was entered and instructing the remote display todisplay an error message if all required information was not entered.12. A remote system, as set forth in claim 11, the player informationincluding a player ID number, the remote network interface fordetermining if the player ID number is valid.
 13. A remote system, asset forth in claim 1, the host computer including a database formaintaining the player tracking system, the remote network interfacecoupled to the database for retrieving and storing data therein.
 14. Aremote system, as set forth in claim 13, the database for storing datain database tables.
 15. A remote system, as set forth in claim 14,further comprising a plurality of first data object coupled to thedatabase tables for retrieving and storing data in the database tables.16. A remote system, as set forth in claim 15, further comprising atleast one second data object coupled to the first data objects forassembling multiple first data objects into a third data object.
 17. Aremote system, as set forth in claim 16, the third data object coupledto the remote network interface for receiving queries from the remotenetwork interface, retrieves responsive data from the database,formatting the responsive data and returning the responsive data to theremote network interface.
 18. A remote system, as set forth in claim 17,the remote network interface for receiving the responsive data andtransmitting the responsive data to the remote device.
 19. A remotesystem, as set forth in claim 18, the remote device having a processorand a web client for interaction with a user, the remote networkinterface for formatting the responsive data into a hyper text mark-uplanguage response for display by the web client.
 20. A remote system, asset forth in claim 6, the web client including a plurality of servletsfor providing functionality to a user.
 21. A remote system, as set forthin claim 20, the web client including a login layer for identifying theuser.
 22. A remote system, as set forth in claim 21, the web clientincluding a menu layer for allowing the user to navigate to and accessthe servlets.
 23. A remote system, as set forth in claim 22, the userhaving an assigned type, the menu layer for allowing accessing toservlets and restricting access to servlets as a function of theassigned type.
 24. A method for adjusting points associated with aplayer in a player tracking system, the method including the steps of:sending an adjustment form to a remote device; filling out the form withdata, by a user, on the remote device for adjusting the pointsassociated with the player in the player tracking system.
 25. A method,as set forth in claim 24, the gaming system including a host computerand a remote network interface for coupling the remote device to thehost computer, including the step of providing a wireless connectionbetween the remote device and the remote network interface.
 26. Amethod, as set forth in claim 25, wherein the wireless connection usesan IEEE 802.11 standard.
 27. A method, as set forth in claim 26, whereinthe wireless connection is IEEE 802.11b.
 28. A method, as set forth inclaim 26, wherein the wireless connection is IEEE 802.11g.
 29. A method,as set forth in claim 25, the remote device having a processor and a webclient for interaction with a user, the method including the steps of:acquiring input via the web client from the user; and, formatting andpresenting data to the user.
 30. A method, as set forth in claim 25, thedata including a signup form, the method including the step of sendingthe point management form to the remote device.
 31. A method, as setforth in claim 36, the data including player ID number, the pointmanagement form being fillable with the player ID by the user, themethod including the step of sending the player ID to a remote networkinterface located on a host computer.
 32. A method, as set forth inclaim 31, the signup form being accessible through the web client.
 33. Amethod, as set forth in claim 32, the method including the step of theconfirming that all required information on the signup form was enteredand instructing a display on the remote display to display an errormessage if all required information was not entered.
 34. A method, asset forth in claim 25, data related to the player tracking system beingstored in a database stored on a host computer, the method including thestep of providing a remote network interface coupled to the database forretrieving and storing data therein.
 35. A method, as set forth in claim34, the method including the step of the storing data in the database indatabase tables.
 36. A method, as set forth in claim 35, the methodincluding the step of providing a plurality of first data object coupledto the database tables for retrieving and storing data in the databasetables.
 37. A method, as set forth in claim 36, the method including thestep of providing at least one second data object coupled to the firstdata objects for assembling multiple first data objects into a thirddata object.
 38. A method, as set forth in claim 37, the third objectbeing coupled to the remote network interface, the method including thesteps of receiving, by the third object, queries from the remote networkinterface, retrieving responsive data from the database, formatting theresponsive data and returning the responsive data to the remote networkinterface.
 39. A method, as set forth in claim 34, the method includingthe step of receiving, by the remote network interface, the responsivedata and transmitting the responsive data to the remote device.
 40. Amethod, as set forth in claim 39, the remote device having a processorand a web client for interaction with a user, the method including thesteps of formatting, by the remote network interface, the responsivedata into a hyper text mark-up language response for display by the webclient.
 41. A method, as set forth in claim 30, the web client includinga plurality of servlets for providing functionality to a user.
 42. Amethod, as set forth in claim 41, the web client including a login layerfor identifying the user.
 43. A method, as set forth in claim 42, theweb client including a menu layer for allowing the user to navigate toand access the servlets.
 44. A method, as set forth in claim 43, theuser having an assigned type, the menu layer for allowing accessing toservlets and restricting access to servlets as a function of theassigned type.